Quote from carmaniac1993 :

Thank you, So far so good. I haven't noticed any random kicks or anything.
I have noticed im still getting alot of these in the lapper logs. "6/19/2014 9:26:21 AM -> Warning packet not catched (55)". It seems to be flooding my log

Any idea on how to make addon. With buttons and a popup msg to appear when a driver spectated?

I have these messages in my logs as well.
Nothing you can't do about them, untill someone picks up the developement of Lapper again.

Which is Event is used to spectate the player?
You could create buttons and messages within that Event, or re-direct the script to another SubEvent.

Quote from Degats :

As a side note, has anyone else had this issue, or is it just something funky with our server/setup?

(Running 0.6E DCon on Ubuntu 12.04.4 via WINE 1.4, haven't tried this latest DCon version yet, will do later)

I think I've seen those errors on my servers as well.
Have been running them on Windows XP and recently changed to server 2008.
Will check tomorrow and report back.

I have taken a look at your LFS dediserver files and noticed there was room for some improvements.
So I made those improvements for you and zipped all the files again.
When you have unzipped the file you will find a shortcut named "start LFS server"
Use that to start your server, as it will point to the config file which is located in the "_config" folder.
I've also created a folder to store the log files in, and made a directory for the replays and layout files.

You do need to set the correct name for your server, as well as the admin password and maybe other port numbers for LFS and InSim, but I think you will be able to handle that

You did disable the Deny button in the last Lapper file you gave me, so that shouldn't be a problem anymore.
I did notice a couple of time-out messages in your Lapper logfile, so I suggest you change a value in your "LFSServers.cfg" file, which is found in the "bin" directory.

Change this: timeOutScript=2000;
To this: timeOutScript=5000;

Then close and start Lapper again.
Let LFS and Lapper run for a while and keep an eye on the log files.

I've inspected your file and found 2 possible moments for a kick to happen:

- When people press the Deny button after having entered the server
- When someone floods the chat

Other then that, no auto-kick events are defined in the file you gave me.
So either your LFS server kicks them for a reason like wrong way driving or using a modified car far, or there are one or more other LFS scripts in place and a kick is coming from there.
Either way, the LFS server log is always showing kicks, so you might be able to find the cause there as well.
If you want me to have a close look at all the files, do the following:

-Make a copy of your LFS directory
-Remove all passwords in the files of that copied directory
-Make a copy of your LFS Lapper directory
-Remove all passwords in the files of that copied directory
-Zip the copied LFS server directory
-Zip the copied LFS Lapper directory
-Upload both files here

If you upload them, I will have a look at the files tomorrow.

Can you upload your lapper file?
Then I am more then happy to have a look at it.

Quote from kepp1313 :

Licence point system is for lfs cruise insim! And i need this!

I'm sorry my friend, but your attitude is wrong.
"I want this" , "I need that" is all we get from you and while people tried to help you, you aren't doing anything your self, except asking for more.
The best way to learn things, is doing them your self and when you really get stuck (and I mean, really!), ask for help and show what you made so far and tell people all you tried to solve the problem your self.
Now go ahead and download LFS Lapper, install it, connect it to your LFS server and then try to write your own code within that environment.
There's enough documentation within Lapper to understand what you need to do and if it's isn't enough, have a look at all the included scripts.

Quote from kepp1313 :

This code is forgin at c++? Or only to lfs lapper?

The code I posted is for LFS Lapper.
As I told you before, if you want to make your own system, coding it within LFS Lapper is the easiest way to do it.
All the Insim commands are already coded for you, so you only need to code buttons, actions, store data, retrieve data etc.

Depends in which system you want to create them.
If it's in an externaly made Insim, you need to write it in the code the Insim is created in.
If it's in LFS Lapper, it needs to go in the following event:

Quote from Scawen :

Yeah, I am sorry about it. But for example this update I am talking about was planned to be before Christmas. But it has simply taken longer than expected. So how would people feel now, in June, if we had said "we will be releasing X before Christmas"...

It's supposed to be soon but look I am already getting in trouble here for just trying to give a vague reply, that this minor addition to InSim could be 'soon'.

I totally understand your feeling, but on the other hand I do think you focus too much on the very vocal and negative part of the LFS community.
Sadly the internet in general has become a large garbage bin over the years and every forum, notice board etc. is littered with moans, aggression, accusations, treats etc. and those people ruin what used to be nice places to read/write.
I agree with you that you shouldn't give dates or maybe even comments like "soon" or "this Christmas" etc, but I also believe that some news from time to time would be a good thing.
Put it in a closed thread or maybe even in a blog where comments are not allowed.
A lot of people like to know what is going on and the single fact that things are going on.
This doesn't have to be a lengthy explanation of what you are exactly doing and it isn't needed to do it on a weekly basis as well.
Just put something on every now and then, like what you are working on, some ideas you have about the (near) future of the game.
Sort of thinking out loud and sharing that with the community.
If people can't handle that, it isn't your fault but theirs and the not (so) vocal part of the community would be grateful for it I'm sure.

Still sounds like connection issues, instead of anything else.
If possible, try it using a direct connection, without any routers/firewalls etc and see if it's working then,
If so, it's a port issue, if not, it could be an issue with your provider.

I can present you the Login & Registration system version 1.02

Which has the following changes:

- Fixed a massive bug in Register and then Login account
- Only show Login button if account is present
- Only show Register button if no account is present
- Show warning about password being send&stored in plain text
- Added button to leave server
- All clickable buttons are shown with yellow text
- Added timer to each screen, to avoid people will stil drive, while screen is left open

Installation instructions:

Download "reg_system.txt"
Rename "reg_system.txt" to "reg_system.lpr"
Replace "reg_system.lpr" in your "bin\includes" folder of your LFS Lapper installation
Restart LFS Lapper

Quote from kepp1313 :

Could you give me the lfs lapper who have already register system?

You are not a "I want to try some things myself" kind of person.
If you want things, the best way to get them done is to try it yourself and when you really get stuck, ask for help.
Here is a version with the login/registration script included.

What you still need to do your self:

- Unzip the attached file
- Make sure insim port 29999 is opened on your LFS Server
- Go to your LFS Lapper folder
- Open folder "bin"
- Open folder "default"
- Open file "defult_1.ini"
- Enter the admin password of your LFS server where you now see "yourpass"
- Safe the file
- Start "LFSLapper.exe" which is foud in the "bin" folder

- Don't forget to thank me for all the help I have given you

Quote from kepp1313 :

Can you make for me?

No I can't.
I have no knowledge of C++ and as said a couple of times now, it isn't needed to do it in C++ either.
LFS Lapper is already a complete environment to run as Insim and can be scripted as much as you want.
Seeing your comments, you haven't got knowledge of C++ either (otherwise you would have coded it your self), so just accept the work I already did by creating just what you asked for in a LFS Lapper script.
It's even better for you, as learning how to code within LFS Lapper, is much easier then having to learn a code like C++

Quote from kepp1313 :

Does this system worked to insim c + +?

No, it runs within LFS Lapper.
So you need to download, install and setup LFS Lapper and then follow the steps I described in my previous posting.

Right, after 2,5 hours of coding and testing, I can present you the Login & Registration system version 1.01
Which has the following features:

- Register account with an accountname and a password
- Check if user already made an account, if so an automatic transfer to login screen
- After account has been succesfuly registered, automatic transfer to login screen
- Login screen with check on both accountname and password
- After 3 false attempts to login, user is kicked from the server

Installation instructions:

Download "reg_system.txt"
Rename "reg_system.txt" to "reg_system.lpr"
Place "reg_system.lpr" in your "bin\includes" folder of your LFS Lapper installation
Open "addonsused.lpr" and add: include( "./reg_system.lpr");

Quote from kepp1313 :

Maybe you have insim witch login / register system?

I don't have that, but I think I can easily create that in Lapper.
Will give it a shot and report back to you.

Quote from kepp1313 :

Maybe you can add yourself to my insim? It will be easier

I have no knowledge of programming, so no clue what to do with the files you included.
All I know is that what you want (registration + login) can easily be written within LFS Lapper.
In fact, all things needed for a Cruise insim, can be done within Lapper.

Quote from kepp1313 :

How do i set up this login/register code?

Look for this event: Event OnMSO( $userName, $text ) # Player event
Then look for this: SWITCH( $command )
Add a new CASE followed by the command you want to register, something like:

Have you considered writing that cruise insim within LFS Lapper?
The things you mentioned so far, can easily be made in LFS Lapper and then saved in a database instead of a TXT file.

I believe the problem is either on the machine hosting our VPS or one of the other VPS's causing a disturbance.
Sadly the technical department of our current ISP isn't willing to look any further into the issue, but now that I know that Server 2008 isn't the cause, we will move on to yet another ISP.
Thanks for your help.

We have tried both the dedicated.exe as the Dcon.exe, but it doesn't make any difference.
We run the server from RDP and we have also tried it with TeamViewer, but that doesn't make any difference either.
We even tried not to run TeamSpeak and not to run LFS Lapper, but still no succes.
It really isn't lag, it are just 3 short freezes and once they are over, the cars are at the same position they were before the freeze started.

Specs:

2 Cores
4 GB memory
150 GB Harddisk
Microsoft Windows Server 2008 R2 Enterprise
Max 5000 GB datatraffic

Recently our team has changed ISP's and while we used to run our servers on a Windows XP (x86) machine, we are now running them on Windows server 2008 R2 (x64).
Since we moved them, we have run into a very nasty issue of having micro stuttering every 15 minutes for three very short moments.
At xx:00 , xx:15 , xx:30 , xx:45 the screens on all clients are freezing for a split second, run on and then freezes two times again.
After that, the car is still at the same position as when the freezing started, so it's not caused by lag.
After having turned our new main server upside down, we haven't found anything that could cause these freezes.
No spikes in CPU use are noticable, no sudden memory spikes, no scheduled tasks that run every 15 minutes.
We tried using the old dedicated server, as well as the latest version and it won't make any difference.

After a lot of communication with our current ISP, they told us that LFS is probably incompatible with Server 2008, while our feeling is that something happens on the main server (all ISP's use shared hosting these days) or that one of our neighbours has something going on every 15 minutes.

Main questions now are:

- Is LFS dedicated server incompatible with Server 2008 R2 (x64)?
- Does anyone else run an LFS server on Server 2008 R2 (x64) and has seen any of these issues?

We are now considering to move to another ISP, but if we would then run into the same problem, it wouldn't help us.
Any help, thoughts, etc. are highly appreciated.

In November 2013 I switched from Lapper 5.x to Lapper 6.x and added my Pubstat keys into the new Lapper.
I also removed the # at the beginning of the line, so all should be fine.
Because our team has moved servers this week, I had to adjust the IP address in LFS World.
While doing that, I noticed that no Pubstat data was used since November 2013.
I double checked my settings in Lapper, even created a new Ident-key to make sure all is working, but still no data seems to be used.
Any ideas on this matter?

Quote from Victor :

No worries.

Pubstat is a means to programmatically retrieve stats from lfs world.
It's all explained in the first post of this thread https://www.lfsforum.net/showthread.php?t=14480
It can be useful for people to collect and show statistics on their own website for example.
You or your team must have been using some application that collected stats, until November when apparently you stopped using the application.

The Keys are inserted into LFS Lapper, which I still use.
It might be that I switched from Lapper 5.x to Lapper 6.x around that time, but then the keys should still work.
I will look into it again as it puzzles me.

*edit*
Indeed, I switched from Lapper 5.x to Lapper 6.x on 16-11-2013.
So that should explain it.
Although the keys are still properly set into the new Lapper as well.
Well, since I haven't heard anyone complain about missing something, I best leave the subject alone I guess.
Thanks for the help.

Last edited by Yisc[NL], Wed 30 Apr 2014, 20:03.

Quote from Victor :

/w pb is an in-game command and has nothing to do with pubstats.

Ow, sorry for the "stupid" comment.
When is pubstat information used?
All I know is that it used data every month consistently and apparently it stopped after November 2013.
Until yesterday the keys were binded to the IP of our previous servers and I changed them to the IP of our new server yesterday evening.